NTISthis.com

Evidence Guide: ICTPRG413 - Use a library or pre-existing components

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG413 - Use a library or pre-existing components

What evidence can you provide to prove your understanding of each of the following citeria?

Identify potential re-use units

  1. Analyse the project design and functionality, to identify re-use components
  2. Source re-use components with the desired functionality
Analyse the project design and functionality, to identify re-use components

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Source re-use components with the desired functionality

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate re-use components for suitability in parent project

  1. Evaluate the re-use component, or libraries, for suitability for use within the parent software project
  2. Compare the functionality of each potential re-use component to the functionality required by the parent project
  3. Evaluate the cost of implementing the re-use component
  4. Consider the technical impact on the parent project design
  5. Consider re-use component vendor licensing issues
  6. Finalise the selection of re-use components
  7. Document selection, evaluation and decision processes, as part of the parent project design documentation
Evaluate the re-use component, or libraries, for suitability for use within the parent software project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare the functionality of each potential re-use component to the functionality required by the parent project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate the cost of implementing the re-use component

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Consider the technical impact on the parent project design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Consider re-use component vendor licensing issues

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Finalise the selection of re-use components

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document selection, evaluation and decision processes, as part of the parent project design documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Incorporate the re-use components

  1. Configure the development environment to include re-use components during the build process
  2. Construct test programs or use provided example programs, to become familiar with re-use components, in preparation for incorporation into the parent project
  3. Add re-use components to the parent project incrementally
  4. Resolve re-use component dependencies
  5. Assemble and test the parent project, with a focus on the functionality provided by the re-use components
Configure the development environment to include re-use components during the build process

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Construct test programs or use provided example programs, to become familiar with re-use components, in preparation for incorporation into the parent project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Add re-use components to the parent project incrementally

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Resolve re-use component dependencies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assemble and test the parent project, with a focus on the functionality provided by the re-use components

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify potential re-use units

1.1 Analyse the project design and functionality, to identify re-use components

1.2 Source re-use components with the desired functionality

2. Evaluate re-use components for suitability in parent project

2.1 Evaluate the re-use component, or libraries, for suitability for use within the parent software project

2.2 Compare the functionality of each potential re-use component to the functionality required by the parent project

2.3 Evaluate the cost of implementing the re-use component

2.4 Consider the technical impact on the parent project design

2.5 Consider re-use component vendor licensing issues

2.6 Finalise the selection of re-use components

2.7 Document selection, evaluation and decision processes, as part of the parent project design documentation

3. Incorporate the re-use components

3.1 Configure the development environment to include re-use components during the build process

3.2 Construct test programs or use provided example programs, to become familiar with re-use components, in preparation for incorporation into the parent project

3.3 Add re-use components to the parent project incrementally

3.4 Resolve re-use component dependencies

3.5 Assemble and test the parent project, with a focus on the functionality provided by the re-use components

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify potential re-use units

1.1 Analyse the project design and functionality, to identify re-use components

1.2 Source re-use components with the desired functionality

2. Evaluate re-use components for suitability in parent project

2.1 Evaluate the re-use component, or libraries, for suitability for use within the parent software project

2.2 Compare the functionality of each potential re-use component to the functionality required by the parent project

2.3 Evaluate the cost of implementing the re-use component

2.4 Consider the technical impact on the parent project design

2.5 Consider re-use component vendor licensing issues

2.6 Finalise the selection of re-use components

2.7 Document selection, evaluation and decision processes, as part of the parent project design documentation

3. Incorporate the re-use components

3.1 Configure the development environment to include re-use components during the build process

3.2 Construct test programs or use provided example programs, to become familiar with re-use components, in preparation for incorporation into the parent project

3.3 Add re-use components to the parent project incrementally

3.4 Resolve re-use component dependencies

3.5 Assemble and test the parent project, with a focus on the functionality provided by the re-use components

Evidence of the ability to:

identify, evaluate, and select the appropriate components that may be re-used

modify and integrate the re-used components into a project

document the selection and evaluation processes

test the functionality of the re-used components.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

define and prepare the contract’s specifications

outline, and apply, current industry development and design methodologies

describe domain modelling

recognise and apply generic specification

define the content and structure of libraries

select and apply the techniques for metrics collection

recognise patterns, frameworks and idioms

identify and apply repository tools.